Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3.0.4: absent, empty, or incomplete security list #4059

Merged
merged 1 commit into from
Sep 2, 2024

Conversation

ralfhandl
Copy link
Contributor

Trying to sum up our lively and highly educating discussion in one sentence - improvement suggestions are welcome.

Part of

@ralfhandl ralfhandl added this to the v3.0.4 milestone Aug 30, 2024
@ralfhandl ralfhandl added security clarification requests to clarify, but not change, part of the spec labels Aug 30, 2024
@ralfhandl ralfhandl requested review from mikekistler, handrews, miqui and a team August 30, 2024 07:27
Copy link
Contributor

@mikekistler mikekistler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. 👍

In future specs we may want something in the intro that explains the whole "open world" concept, but for now I think this addresses the specific concern with an empty security array.

@ralfhandl ralfhandl merged commit 0056446 into OAI:v3.0.4-dev Sep 2, 2024
1 check passed
@ralfhandl ralfhandl deleted the 3.0.4-omitted-or-empy-security branch September 2, 2024 07:11
@ralfhandl ralfhandl linked an issue Sep 3, 2024 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification requests to clarify, but not change, part of the spec security
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clarification about the meaning of an empty security array
3 participants